chore(deps): Bump base64 from 0.22.1 to 0.23.1 - #380
Conversation
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
gnanirahulnutakki
left a comment
gnanirahulnutakki
left a comment
There was a problem hiding this comment.
Reviewed exact head 260c8ce against dev@a42ffe0f.
Direct workspace consumers resolve to base64 0.23.0; retained 0.22.1 entries are transitive. The wider lockfile change is reproducible workspace reconciliation: full cargo metadata --locked fails on the base lock but succeeds on this head, adding the active delegate/durability closure and removing orphan non-workspace entries.
All Ardur callsites still use the unchanged scalar GeneralPurpose STANDARD/URL_SAFE_NO_PAD engines, with no matching on the changed decode-error variant. The workspace toolchain exceeds the new MSRV, and current advisory checks found no applicable issue in the changed package set. Exact-head workspace, cargo-deny, dependency review, CodeQL, Docker/SBOM/Trivy, and DCO gates are green; focused receipt/media/web/webhook tests also pass with --locked. No blocking findings.
dependabot
Bot
changed the title
260c8ce to
a1c8ca2
Compare
gnanirahulnutakki
left a comment
gnanirahulnutakki
left a comment
There was a problem hiding this comment.
Re-reviewed exact head a1c8ca28 against dev@4715a4d. The refreshed diff is narrow and reproducible: resolving the workspace manifest bump from the exact base adds only base64 0.23.1, retargets the nine active direct workspace edges, and produces byte-identical Cargo.toml/Cargo.lock; retained 0.22.1 and 0.13.1 entries are transitive. Compared with the previously reviewed 260c8ced (0.23.0), base64 0.23.1 has no production-source changes and only fixes its non-SIMD test configuration, with unchanged MSRV. Exact-head formatting, all nine direct-consumer unit/integration/doc suites, cargo-deny, diff checks, and all hosted checks pass. No blocking findings.
a1c8ca2 to
9f75c23
Compare
Bumps [base64](https://github.com/marshallpierce/rust-base64) from 0.22.1 to 0.23.1. - [Changelog](https://github.com/marshallpierce/rust-base64/blob/master/RELEASE-NOTES.md) - [Commits](marshallpierce/rust-base64@v0.22.1...v0.23.1) --- updated-dependencies: - dependency-name: base64 dependency-version: 0.23.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
9f75c23 to
8aca9d8
Compare
Adds crates/code-execution (ardur-code-execution), Phase 1 of the §6.7
code-execution blueprint: a closed LanguageAdapter trait with Bash and
Python adapters, a cap-token-shaped CodeExecutionCaveat that attenuates
every request (language allowlist, timeout ceiling, tool-callback
allowlist intersection that never widens, forced expose_stderr override,
output-size ceiling), a code.exec.{requested,completed,failed,tool_denied}.v1
receipt forest, and a CodeExecutionTool (code.exec) gated by
Capability::ProcessSpawn plus a custom code_execution capability that
scans captured stdout through ardur-injection-defense before returning it.
Tool-call RPC (a running script dispatching back into the tool registry),
Node/Rust adapters, and routing through the §6.3 backend matrix / §11.5
sandbox runtime are out of scope here — none of those crates exist yet in
this workspace. Documented as explicit Phase 2 TODOs; every dispatch in
this crate is unsandboxed local process execution until §11.5 lands.
Browser automation (§6.9/§6.10) already ships as crates/browser and is
not duplicated here.
Checkpoint: architect/sessions/2026-07-14-code-execution-6.7/journal.md
Rebase note: squashed onto current `dev`; the only conflict was the workspace
`base64` pin, resolved to `dev`'s `0.23` (raised by #380) rather than the
branch's stale `0.22`.
Signed-off-by: GR <gnanirn@gmail.com>
Adds crates/code-execution (ardur-code-execution), Phase 1 of the §6.7
code-execution blueprint: a closed LanguageAdapter trait with Bash and
Python adapters, a cap-token-shaped CodeExecutionCaveat that attenuates
every request (language allowlist, timeout ceiling, tool-callback
allowlist intersection that never widens, forced expose_stderr override,
output-size ceiling), a code.exec.{requested,completed,failed,tool_denied}.v1
receipt forest, and a CodeExecutionTool (code.exec) gated by
Capability::ProcessSpawn plus a custom code_execution capability that
scans captured stdout through ardur-injection-defense before returning it.
Tool-call RPC (a running script dispatching back into the tool registry),
Node/Rust adapters, and routing through the §6.3 backend matrix / §11.5
sandbox runtime are out of scope here — none of those crates exist yet in
this workspace. Documented as explicit Phase 2 TODOs; every dispatch in
this crate is unsandboxed local process execution until §11.5 lands.
Browser automation (§6.9/§6.10) already ships as crates/browser and is
not duplicated here.
Checkpoint: architect/sessions/2026-07-14-code-execution-6.7/journal.md
Rebase note: squashed onto current `dev`; the only conflict was the workspace
`base64` pin, resolved to `dev`'s `0.23` (raised by #380) rather than the
branch's stale `0.22`.
Signed-off-by: GR <gnanirn@gmail.com>
1 participant
Bumps base64 from 0.22.1 to 0.23.1.
Changelog
Sourced from base64's changelog.
Commits
069bf70v0.23.16ab1fb0Merge pull request #310 from musicinmybrain/test-on-non-simd-arches7cffce6Fix testing on architectures without unsafe SIMD supporte34f9a0Merge pull request #308 from atouchet/come9240c9Remove outdated comment9e9220av0.23.0870326eMerge pull request #306 from marshallpierce/mp/trailing-bits-docsfbec5f1Document no trailing trailing bits0a23549Merge pull request #305 from marshallpierce/mp/edition-2021f10b7e2Update deps & edition